Markup Validation Service

Validation Output: 455 Errors

1. Line 24, Column 47: end tag for "meta" omitted, but OMITTAG NO was specified

   …="y_key" content="1d8b62e6da1997a…

   ✉

   You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

2. Line 24: start tag was here

   ><meta name="y_key" content="1d8b62e6da1997ab">

3. Line 169, Column 299: character "&" is the first character of a delimiter but occurred as data

   …type="text/javascript">    if (!nad && typeof(window["GS_googleAddAdSenseServ

   ✉

   This message may appear in several cases:

   • You tried to include the "<" character in your page: you should escape it as "&lt;"
   • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
   • Another possibility is that you forgot to close quotes in a previous tag.
4. Line 169, Column 300: character "&amp;" is the first character of a delimiter but occurred as data

   …ype="text/javascript">    if (!nad && typeof(window["GS_googleAddAdSenseServi

   ✉

   This message may appear in several cases:

   • You tried to include the "<" character in your page: you should escape it as "&lt;"
   • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
   • Another possibility is that you forgot to close quotes in a previous tag.
5. Line 244, Column 31: an attribute value must be a literal unless it contains only name characters

   document.writeln('<style type=\"text/css\">');

   ✉

   You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

6. Line 244, Column 43: document type does not allow element "style" here

   document.writeln('<style type=\"text/css\">');

   ✉

   The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

   One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

7. Line 328, Column 71: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

   …" class="txt" type="text" value="" /> <a onclick="if ($('#txt_searchBox')[0].

   ✉

   The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

   One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

8. Line 328, Column 187: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

   …('#fm_Search').submit();};" href="#"><img alt="Search" src="/gfx/00/07/40/bt-

   ✉

   The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

   One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

9. Line 1121, Column 82: character "&amp;" is the first character of a delimiter but occurred as data

   …chedule---results/" title="Schedule & Results">Schedule & Results</a></li>

   ✉

   This message may appear in several cases:

   • You tried to include the "<" character in your page: you should escape it as "&lt;"
   • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
   • Another possibility is that you forgot to close quotes in a previous tag.
10. Line 1121, Column 102: character "&amp;" is the first character of a delimiter but occurred as data

    …title="Schedule & Results">Schedule & Results</a></li>

    ✉

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
11. Line 1225, Column 20: Attribute "language" exists, but can not be used for this element.

    		<script language="JavaScript" type="text/javascript">

    ✉

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

12. Line 1232, Column 28: an attribute value must be a literal unless it contains only name characters

    document.write("<div style=\"position:relative; height: 293px;\"><div style=\"po

    ✉

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

13. Line 1232, Column 57: "height:" is not a member of a group specified for any attribute

    … style=\"position:relative; height: 293px;\"><div style=\"position:absolute; 

    ✉

14. Line 1232, Column 57: "293px" is not a member of a group specified for any attribute

    … style=\"position:relative; height: 293px;\"><div style=\"position:absolute; 

    ✉

15. Line 1232, Column 65: document type does not allow element "div" here

    …"position:relative; height: 293px;\"><div style=\"position:absolute; left: -1

    ✉

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

16. Line 1232, Column 77: an attribute value must be a literal unless it contains only name characters

    …:relative; height: 293px;\"><div style=\"position:absolute; left: -19px;\">");

    ✉

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

17. Line 1232, Column 104: "left:" is not a member of a group specified for any attribute

    …iv style=\"position:absolute; left: -19px;\">");

    ✉

18. Line 1232, Column 104: "-19px" is not a member of a group specified for any attribute

    …iv style=\"position:absolute; left: -19px;\">");

    ✉

19. Line 1416, Column 174: required attribute "alt" not specified

    …/72/97175612-10_56imgGalTh-zp.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

20. Line 1511, Column 373: required attribute "alt" not specified

    …/29/73/97176776_58imgGalTh-ee.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

21. Line 1520, Column 293: required attribute "alt" not specified

    …/72/97175612-10_56imgGalTh-zp.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

22. Line 1529, Column 353: required attribute "alt" not specified

    …/72/97175583-10_54imgGalTh-xm.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

23. Line 1538, Column 413: required attribute "alt" not specified

    …/72/97175720-10_52imgGalTh-MR.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

24. Line 1547, Column 287: required attribute "alt" not specified

    …/72/97175242-10_44imgGalTh-jl.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

25. Line 1556, Column 303: required attribute "alt" not specified

    …/72/97175229-10_42imgGalTh-Vg.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

26. Line 1575, Column 293: required attribute "alt" not specified

    …/72/97175064-10_40imgGalTh-Qf.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

27. Line 1584, Column 287: required attribute "alt" not specified

    …/72/97175203-10_38imgGalTh-Mh.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

28. Line 1593, Column 303: required attribute "alt" not specified

    …/72/97174956-10_36imgGalTh-Qd.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

29. Line 1602, Column 239: required attribute "alt" not specified

    …/72/97174688-10_30imgGalTh-yx.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

30. Line 1611, Column 299: required attribute "alt" not specified

    …/72/97174671-10_28imgGalTh-oY.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

31. Line 1620, Column 293: required attribute "alt" not specified

    …/72/97174555-10_26imgGalTh-tz.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

32. Line 1639, Column 211: required attribute "alt" not specified

    …/29/71/97148394_18imgGalTh-bf.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

33. Line 1648, Column 211: required attribute "alt" not specified

    …/29/71/97148392_20imgGalTh-CK.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

34. Line 1657, Column 211: required attribute "alt" not specified

    …/29/71/97148366_22imgGalTh-HZ.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

35. Line 1666, Column 211: required attribute "alt" not specified

    …/29/71/97148208_24imgGalTh-fG.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

36. Line 1675, Column 211: required attribute "alt" not specified

    …/29/71/97148218_26imgGalTh-hh.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

37. Line 1684, Column 211: required attribute "alt" not specified

    …/29/71/97147899_28imgGalTh-ZR.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

38. Line 1703, Column 211: required attribute "alt" not specified

    …/29/71/97147733_00imgGalTh-XC.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

39. Line 1712, Column 211: required attribute "alt" not specified

    …/29/71/97147849_30imgGalTh-eR.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

40. Line 1721, Column 211: required attribute "alt" not specified

    …/29/71/97147676_02imgGalTh-Fy.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

41. Line 1730, Column 211: required attribute "alt" not specified

    …/29/71/97147611_04imgGalTh-eF.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

42. Line 1739, Column 211: required attribute "alt" not specified

    …/29/71/97147437_10imgGalTh-kg.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

43. Line 1748, Column 211: required attribute "alt" not specified

    …/29/71/97147515_12imgGalTh-Kn.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

44. Line 1767, Column 211: required attribute "alt" not specified

    …/29/71/97147224_14imgGalTh-bS.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

45. Line 1776, Column 211: required attribute "alt" not specified

    …/29/71/97147199_16imgGalTh-PP.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

46. Line 1785, Column 303: required attribute "alt" not specified

    …/29/70/97150393_80imgGalTh-Nd.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

47. Line 1794, Column 303: required attribute "alt" not specified

    …/29/70/97149657_88imgGalTh-yM.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

48. Line 1803, Column 303: required attribute "alt" not specified

    …/29/70/97150023_94imgGalTh-ZI.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

49. Line 1812, Column 303: required attribute "alt" not specified

    …/29/70/97150219_74imgGalTh-bV.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

50. Line 1873, Column 67: cannot generate system identifier for general entity "utm_medium"

    …010.com/store/?utm_campaign=believe&utm_medium=banner&utm_source=main&utm_con

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

51. Line 1873, Column 67: general entity "utm_medium" not defined and no default entity

    …010.com/store/?utm_campaign=believe&utm_medium=banner&utm_source=main&utm_con

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

52. Line 1873, Column 77: reference not terminated by REFC delimiter

    …ore/?utm_campaign=believe&utm_medium=banner&utm_source=main&utm_content=en" t

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

53. Line 1873, Column 77: reference to external entity in attribute value

    …ore/?utm_campaign=believe&utm_medium=banner&utm_source=main&utm_content=en" t

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

54. Line 1873, Column 77: reference to entity "utm_medium" for which no system identifier could be generated

    …ore/?utm_campaign=believe&utm_medium=banner&utm_source=main&utm_content=en" t

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

55. Line 1873, Column 65: entity was defined here

    …r2010.com/store/?utm_campaign=believe&utm_medium=banner&utm_source=main&utm_c

56. Line 1873, Column 85: cannot generate system identifier for general entity "utm_source"

    …_campaign=believe&utm_medium=banner&utm_source=main&utm_content=en" title="Be

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

57. Line 1873, Column 85: general entity "utm_source" not defined and no default entity

    …_campaign=believe&utm_medium=banner&utm_source=main&utm_content=en" title="Be

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

58. Line 1873, Column 95: reference not terminated by REFC delimiter

    …believe&utm_medium=banner&utm_source=main&utm_content=en" title="Believe in O

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

59. Line 1873, Column 95: reference to external entity in attribute value

    …believe&utm_medium=banner&utm_source=main&utm_content=en" title="Believe in O

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

60. Line 1873, Column 95: reference to entity "utm_source" for which no system identifier could be generated

    …believe&utm_medium=banner&utm_source=main&utm_content=en" title="Believe in O

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

61. Line 1873, Column 83: entity was defined here

    …tm_campaign=believe&utm_medium=banner&utm_source=main&utm_content=en" title="

62. Line 1873, Column 101: cannot generate system identifier for general entity "utm_content"

    …e&utm_medium=banner&utm_source=main&utm_content=en" title="Believe in Olympic

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

63. Line 1873, Column 101: general entity "utm_content" not defined and no default entity

    …e&utm_medium=banner&utm_source=main&utm_content=en" title="Believe in Olympic

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

64. Line 1873, Column 112: reference not terminated by REFC delimiter

    …m=banner&utm_source=main&utm_content=en" title="Believe in Olympic Heroes"><i

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

65. Line 1873, Column 112: reference to external entity in attribute value

    …m=banner&utm_source=main&utm_content=en" title="Believe in Olympic Heroes"><i

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

66. Line 1873, Column 112: reference to entity "utm_content" for which no system identifier could be generated

    …m=banner&utm_source=main&utm_content=en" title="Believe in Olympic Heroes"><i

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

67. Line 1873, Column 99: entity was defined here

    …eve&utm_medium=banner&utm_source=main&utm_content=en" title="Believe in Olymp

68. Line 1873, Column 216: required attribute "alt" not specified

    …ve-mainsite-banner-eng_22d-iV.jpg" /></a>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

69. Line 1898, Column 37: character "&amp;" is the first character of a delimiter but occurred as data

      if (!(typeof nad === "undefined") && !nad)

    ✉

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
70. Line 1898, Column 38: character "&amp;" is the first character of a delimiter but occurred as data

      if (!(typeof nad === "undefined") && !nad)

    ✉

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
71. Line 1970, Column 169: required attribute "alt" not specified

    …eo--22---day-17_70imgGalTh-HZ.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

72. Line 2016, Column 169: required attribute "alt" not specified

    …eo--21---day-16_92imgGalTh-fO.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

73. Line 2062, Column 173: required attribute "alt" not specified

    …w-year-richmond_76imgGalTh-rp.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

74. Line 2158, Column 107: required attribute "alt" not specified

    …0/09/57/culture_42imgGalTh-ch.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

75. Line 2199, Column 158: required attribute "alt" not specified

    …g/00/09/57/code_46imgGalTh-bA.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

76. Line 2254, Column 180: required attribute "alt" not specified

    …29/19/frontcrop_76imgGalTh-mZ.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

77. Line 2312, Column 353: required attribute "alt" not specified

    …vertical-align:middle !important;" /> Vancouver 2010 </a><br /><a href="http:

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

78. Line 2312, Column 542: required attribute "alt" not specified

    …vertical-align:middle !important;" /> Cultural Olympiad</a></div>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

79. Line 2313, Column 300: required attribute "alt" not specified

    …vertical-align:middle !important;" /> Vancouver 2010</a><br />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

80. Line 2314, Column 148: required attribute "alt" not specified

    …vertical-align:middle !important;" /> Torch Relay</a><br />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

81. Line 2315, Column 142: required attribute "alt" not specified

    …vertical-align:middle !important;" /> CODE 2010</a>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

82. Line 2340, Column 37: character "&amp;" is the first character of a delimiter but occurred as data

      if (!(typeof nad === "undefined") && !nad)

    ✉

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
83. Line 2340, Column 38: character "&amp;" is the first character of a delimiter but occurred as data

      if (!(typeof nad === "undefined") && !nad)

    ✉

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
84. Line 2454, Column 17: ID "x" already defined

    								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

85. Line 2420, Column 17: ID "x" first defined here

             <tr id="x">

86. Line 2468, Column 17: ID "x" already defined

    								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

87. Line 2420, Column 17: ID "x" first defined here

             <tr id="x">

88. Line 2482, Column 17: ID "x" already defined

    								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

89. Line 2420, Column 17: ID "x" first defined here

             <tr id="x">

90. Line 2496, Column 17: ID "x" already defined

    								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

91. Line 2420, Column 17: ID "x" first defined here

             <tr id="x">

92. Line 2510, Column 17: ID "x" already defined

    								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

93. Line 2420, Column 17: ID "x" first defined here

             <tr id="x">

94. Line 2524, Column 17: ID "x" already defined

    								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

95. Line 2420, Column 17: ID "x" first defined here

             <tr id="x">

96. Line 2538, Column 17: ID "x" already defined

    								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

97. Line 2420, Column 17: ID "x" first defined here

             <tr id="x">

98. Line 2552, Column 17: ID "x" already defined

    								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

99. Line 2420, Column 17: ID "x" first defined here

             <tr id="x">

100. Line 2566, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

101. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

102. Line 2580, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

103. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

104. Line 2603, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

105. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

106. Line 2617, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

107. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

108. Line 2631, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

109. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

110. Line 2645, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

111. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

112. Line 2659, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

113. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

114. Line 2673, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

115. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

116. Line 2687, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

117. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

118. Line 2701, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

119. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

120. Line 2715, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

121. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

122. Line 2729, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

123. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

124. Line 2752, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

125. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

126. Line 2766, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

127. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

128. Line 2780, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

129. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

130. Line 2794, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

131. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

132. Line 2808, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

133. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

134. Line 2822, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

135. Line 2420, Column 17: ID "x" first defined here

              <tr id="x">

136. Line 2853, Column 120: Attribute "target" exists, but can not be used for this element.

     …this widget on your website" target="_top"><img src="/gfx/00/27/06/widgetmeda

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

137. Line 2853, Column 182: required attribute "alt" not specified

     …7/06/widgetmedalsembed_86d-JB.gif" /></a></span>

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

138. Line 2856, Column 146: required attribute "alt" not specified

     …gfx/00/18/42/medalshp1_54d-so.gif" /></a>

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

139. Line 2891, Column 37: character "&amp;" is the first character of a delimiter but occurred as data

       if (!(typeof nad === "undefined") && !nad)

     ✉

     This message may appear in several cases:

     • You tried to include the "<" character in your page: you should escape it as "&lt;"
     • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
     • Another possibility is that you forgot to close quotes in a previous tag.
140. Line 2891, Column 38: character "&amp;" is the first character of a delimiter but occurred as data

       if (!(typeof nad === "undefined") && !nad)

     ✉

     This message may appear in several cases:

     • You tried to include the "<" character in your page: you should escape it as "&lt;"
     • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
     • Another possibility is that you forgot to close quotes in a previous tag.
141. Line 2916, Column 9: required attribute "type" not specified

     		<style>

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

142. Line 2916, Column 9: document type does not allow element "style" here

     		<style>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

143. Line 2924, Column 12: Attribute "name" exists, but can not be used for this element.

     <form name="#">

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

144. Line 2924, Column 15: required attribute "action" not specified

     <form name="#">

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

145. Line 2925, Column 172: document type does not allow element "select" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

     …lue) location.href = selectedValue;">

     ✉

     The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

     One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

146. Line 2928, Column 71: cannot generate system identifier for general entity "cat1"

     …guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation A

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

147. Line 2928, Column 71: general entity "cat1" not defined and no default entity

     …guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation A

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

148. Line 2928, Column 75: reference not terminated by REFC delimiter

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alert

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

149. Line 2928, Column 75: reference to external entity in attribute value

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alert

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

150. Line 2928, Column 75: reference to entity "cat1" for which no system identifier could be generated

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alert

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

151. Line 2928, Column 69: entity was defined here

     …r-guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation

152. Line 2928, Column 83: cannot generate system identifier for general entity "q"

     …/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

153. Line 2928, Column 83: general entity "q" not defined and no default entity

     …/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

154. Line 2928, Column 84: reference not terminated by REFC delimiter

     …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

155. Line 2928, Column 84: reference to external entity in attribute value

     …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

156. Line 2928, Column 84: reference to entity "q" for which no system identifier could be generated

     …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

157. Line 2928, Column 81: entity was defined here

     …ts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opt

158. Line 2928, Column 86: cannot generate system identifier for general entity "start"

     …dex_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

159. Line 2928, Column 86: general entity "start" not defined and no default entity

     …dex_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

160. Line 2928, Column 91: reference not terminated by REFC delimiter

     …f-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

161. Line 2928, Column 91: reference to external entity in attribute value

     …f-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

162. Line 2928, Column 91: reference to entity "start" for which no system identifier could be generated

     …f-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

163. Line 2928, Column 84: entity was defined here

     …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

164. Line 2929, Column 75: reference not terminated by REFC delimiter

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alert

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

165. Line 2929, Column 75: reference to external entity in attribute value

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alert

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

166. Line 2929, Column 75: reference to entity "cat1" for which no system identifier could be generated

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alert

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

167. Line 2928, Column 69: entity was defined here

     …r-guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation

168. Line 2929, Column 84: reference not terminated by REFC delimiter

     …index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</opti…

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

169. Line 2929, Column 84: reference to external entity in attribute value

     …index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</opti…

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

170. Line 2929, Column 84: reference to entity "q" for which no system identifier could be generated

     …index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</opti…

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

171. Line 2928, Column 81: entity was defined here

     …ts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opt

172. Line 2929, Column 91: reference not terminated by REFC delimiter

     …f-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</option>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

173. Line 2929, Column 91: reference to external entity in attribute value

     …f-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</option>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

174. Line 2929, Column 91: reference to entity "start" for which no system identifier could be generated

     …f-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</option>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

175. Line 2928, Column 84: entity was defined here

     …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

176. Line 2930, Column 75: reference not terminated by REFC delimiter

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</op

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

177. Line 2930, Column 75: reference to external entity in attribute value

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</op

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

178. Line 2930, Column 75: reference to entity "cat1" for which no system identifier could be generated

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</op

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

179. Line 2928, Column 69: entity was defined here

     …r-guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation

180. Line 2930, Column 84: reference not terminated by REFC delimiter

     …index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

181. Line 2930, Column 84: reference to external entity in attribute value

     …index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

182. Line 2930, Column 84: reference to entity "q" for which no system identifier could be generated

     …index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

183. Line 2928, Column 81: entity was defined here

     …ts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opt

184. Line 2930, Column 91: reference not terminated by REFC delimiter

     …f-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

185. Line 2930, Column 91: reference to external entity in attribute value

     …f-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

186. Line 2930, Column 91: reference to entity "start" for which no system identifier could be generated

     …f-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

187. Line 2928, Column 84: entity was defined here

     …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

188. Line 3101, Column 15: required attribute "action" not specified

     <form name="#">

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

189. Line 3102, Column 13: ID "drp_filter" already defined

     <select id="drp_filter" name="drp_filter drp_nojs" onchange="var selectedValue =

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

190. Line 2925, Column 12: ID "drp_filter" first defined here

     <select id="drp_filter" name="drp_filter drp_nojs" onchange="var selectedValue =

191. Line 3102, Column 231: document type does not allow element "select" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

     …h: 280px !important; color:#0076CC;">

     ✉

     The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

     One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

192. Line 3104, Column 3: "DOCTYPE" declaration not allowed in instance

     <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.or

     ✉

193. Line 3105, Column 43: document type does not allow element "html" here

     <html xmlns="http://www.w3.org/1999/xhtml">

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

194. Line 3111, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Albania  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

195. Line 3112, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Albania  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

196. Line 3113, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Algeria  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

197. Line 3114, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Algeria  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

198. Line 3115, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Andorra  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

199. Line 3116, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Andorra  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

200. Line 3117, Column 65: document type does not allow element "option" here

     …="http://www.ar.terra.com/deportes/vancouver2010/" >Argentina - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

201. Line 3118, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Armenia  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

202. Line 3119, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Armenia  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

203. Line 3120, Column 42: document type does not allow element "option" here

     <option value="http://www.nos.nl/os2010" >Aruba - NOS</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

204. Line 3121, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Aruba  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

205. Line 3122, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Aruba - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

206. Line 3123, Column 56: document type does not allow element "option" here

     <option value="http://www.foxtel.com.au/vancouver2010" >Australia - Foxtel</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

207. Line 3124, Column 49: document type does not allow element "option" here

     <option value="http://ninemsn.com.au/vancouver" >Australia - Nine</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

208. Line 3125, Column 48: document type does not allow element "option" here

     <option value="http://de.eurosport.yahoo.com " >Austria  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

209. Line 3126, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Austria - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

210. Line 3127, Column 37: document type does not allow element "option" here

     <option value="http://sport.orf.at" >Austria - ORF</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

211. Line 3128, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Azerbaijan  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

212. Line 3129, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Azerbaijan  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

213. Line 3130, Column 44: document type does not allow element "option" here

     <option value="http://olimpicgames.tvr.by" >Belarus -TVR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

214. Line 3131, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Belarus  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

215. Line 3132, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Belarus - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

216. Line 3133, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Belgium  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

217. Line 3134, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Belgium - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

218. Line 3135, Column 42: document type does not allow element "option" here

     <option value="http://www.rtbf.be/sport" >Belgium - RTBF</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

219. Line 3136, Column 76: document type does not allow element "option" here

     …/cm/sporza/ander_nieuws/Vancouver_2010" >Belgium - VRT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

220. Line 3137, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Bosnia and Herzegovina</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

221. Line 3138, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >Bosnia and Herzegovina - Eurovision</opt

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

222. Line 3139, Column 60: document type does not allow element "option" here

     <option value="http://esportes.terra.com.br/vancouver2010" >Brazil - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

223. Line 3140, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >British Indian Ocean Territory</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

224. Line 3141, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >British Indian Ocean Territory  - Eurovi

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

225. Line 3142, Column 38: document type does not allow element "option" here

     <option value="http://winter.bnt.bg" >Bulgaria - BNT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

226. Line 3143, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Bulgaria  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

227. Line 3144, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Bulgaria - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

228. Line 3145, Column 43: document type does not allow element "option" here

     <option value="http://www.ctvolympics.ca" >Canada - CTV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

229. Line 3146, Column 45: document type does not allow element "option" here

     <option value="http://www.rdsolympiques.ca" >Canada - RDS</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

230. Line 3147, Column 51: document type does not allow element "option" here

     <option value="http://www.rtve.es/vancouver-2010" >Canary Islands - RTVE</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

231. Line 3148, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Canary Islands  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

232. Line 3149, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Canary Islands - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

233. Line 3150, Column 65: document type does not allow element "option" here

     …="http://www.cl.terra.com/deportes/vancouver2010/" >Chile - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

234. Line 3151, Column 39: document type does not allow element "option" here

     <option value="http://sports.cntv.cn" >China, People's Republic of - CCTV</opti…

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

235. Line 3152, Column 57: document type does not allow element "option" here

     <option value="http://www.elta.tv/event/Vancouver2010/" >Chinese Taipei - ELTA</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

236. Line 3153, Column 65: document type does not allow element "option" here

     …="http://www.co.terra.com/deportes/vancouver2010/" >Colombia - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

237. Line 3154, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >Costa Rica - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

238. Line 3155, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Croatia  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

239. Line 3156, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Croatia  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

240. Line 3157, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Cyprus  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

241. Line 3158, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Cyprus  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

242. Line 3159, Column 45: document type does not allow element "option" here

     <option value="http://www.ceskatelevize.cz" >Czech Republic - ceskatelevize</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

243. Line 3160, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Czech Republic  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

244. Line 3161, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Czech Republic - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

245. Line 3162, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Denmark  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

246. Line 3163, Column 42: document type does not allow element "option" here

     <option value="http://www.dr.dk/sporten" >Denmark - DR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

247. Line 3164, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Denmark - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

248. Line 3165, Column 42: document type does not allow element "option" here

     <option value="http://www.ol2010.tv2.dk" >Denmark - TV2</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

249. Line 3166, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >Dominican Republic</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

250. Line 3167, Column 65: document type does not allow element "option" here

     …="http://www.ec.terra.com/deportes/vancouver2010/" >Ecuador - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

251. Line 3168, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Egypt  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

252. Line 3169, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Egypt  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

253. Line 3170, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >El Salvador - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

254. Line 3171, Column 39: document type does not allow element "option" here

     <option value="http://www.err.ee/om/" >Estonia - ERR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

255. Line 3172, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Estonia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

256. Line 3173, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Estonia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

257. Line 3174, Column 44: document type does not allow element "option" here

     … value="http://eurosport.yahoo.com" >Falkland Islands (Malvinas)  - Eurosport

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

258. Line 3175, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >Falkland Islands (Malvinas) - Eurovision

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

259. Line 3176, Column 42: document type does not allow element "option" here

     <option value="http://www.dr.dk/sporten" >Faroe Islands - DR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

260. Line 3177, Column 42: document type does not allow element "option" here

     <option value="http://www.ol2010.tv2.dk" >Faroe Islands - TV2</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

261. Line 3178, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Faroe Islands - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

262. Line 3179, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Faroe Islands - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

263. Line 3180, Column 31: document type does not allow element "option" here

     <option value="http://yle.fi" >Finland - YLE</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

264. Line 3181, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Finland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

265. Line 3182, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Finland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

266. Line 3183, Column 44: document type does not allow element "option" here

     … value="http://eurosport.yahoo.com" >Former Yugoslav Rep. of Macedonia - Euro

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

267. Line 3184, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >Former Yugoslav Rep. of Macedonia - Euro

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

268. Line 3185, Column 54: document type does not allow element "option" here

     <option value="http://jo-vancouver-2010.francetv.fr" >France - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

269. Line 3186, Column 38: document type does not allow element "option" here

     <option value="http://eurosport.fr " >France - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

270. Line 3187, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >France - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

271. Line 3188, Column 54: document type does not allow element "option" here

     …tp://jo-vancouver-2010.francetv.fr" >French Guyana - France Télévisions</opti

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

272. Line 3189, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >French Guyana - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

273. Line 3190, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >French Guyana - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

274. Line 3191, Column 54: document type does not allow element "option" here

     …tp://jo-vancouver-2010.francetv.fr" >French Polynesia - France Télévisions</o

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

275. Line 3192, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >French Polynesia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

276. Line 3193, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >French Polynesia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

277. Line 3194, Column 54: document type does not allow element "option" here

     …tp://jo-vancouver-2010.francetv.fr" >French Southern Territories  - France Té

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

278. Line 3195, Column 44: document type does not allow element "option" here

     … value="http://eurosport.yahoo.com" >French Southern Territories - Eurosport<

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

279. Line 3196, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >French Southern Territories - Eurovision

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

280. Line 3197, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Georgia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

281. Line 3198, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Georgia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

282. Line 3199, Column 48: document type does not allow element "option" here

     <option value="http://de.eurosport.yahoo.com " >Germany - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

283. Line 3200, Column 39: document type does not allow element "option" here

     <option value="http://olympia.ard.de" >Germany - ARD</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

284. Line 3201, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Germany - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

285. Line 3202, Column 39: document type does not allow element "option" here

     <option value="http://olympia.zdf.de" >Germany - ZDF</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

286. Line 3203, Column 44: document type does not allow element "option" here

     <option value="http://www.bbc.co.uk/sport" >Gibraltar - BBC</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

287. Line 3204, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Gibraltar - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

288. Line 3205, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Gibraltar - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

289. Line 3206, Column 56: document type does not allow element "option" here

     <option value="http://news.ert.gr/sports/olympics2010" >Greece - ERT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

290. Line 3207, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Greece - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

291. Line 3208, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Greece - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

292. Line 3209, Column 42: document type does not allow element "option" here

     <option value="http://www.dr.dk/sporten" >Greenland - DR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

293. Line 3210, Column 42: document type does not allow element "option" here

     <option value="http://www.ol2010.tv2.dk" >Greenland - TV2</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

294. Line 3211, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Greenland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

295. Line 3212, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Greenland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

296. Line 3213, Column 54: document type does not allow element "option" here

     …tp://jo-vancouver-2010.francetv.fr" >Guadeloupe - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

297. Line 3214, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Guadeloupe - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

298. Line 3215, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Guadeloupe - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

299. Line 3216, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >Guatemala - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

300. Line 3217, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >Honduras - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

301. Line 3218, Column 40: document type does not allow element "option" here

     <option value="http://www.i-cable.com" >Hong Kong - i-Cable</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

302. Line 3219, Column 43: document type does not allow element "option" here

     <option value="http://www.teliolimpia.hu" >Hungary - Magyar</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

303. Line 3220, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Hungary - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

304. Line 3221, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Hungary - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

305. Line 3222, Column 42: document type does not allow element "option" here

     <option value="http://www.ruv.is/ol2010" >Iceland - RUV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

306. Line 3223, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Iceland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

307. Line 3224, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Iceland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

308. Line 3225, Column 47: document type does not allow element "option" here

     <option value="http://uk.eurosport.yahoo.com" >Ireland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

309. Line 3226, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Ireland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

310. Line 3227, Column 45: document type does not allow element "option" here

     <option value="http://www.iba.org.il/sport" >Israel - IBA</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

311. Line 3228, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Israel - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

312. Line 3229, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Israel - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

313. Line 3230, Column 49: document type does not allow element "option" here

     <option value="http://www.vancouver2010.rai.it" >Italy - Rai</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

314. Line 3231, Column 45: document type does not allow element "option" here

     <option value="http://www.sky.it/olimpiadi" >Italy - Sky Italia</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

315. Line 3232, Column 37: document type does not allow element "option" here

     <option value="http://www.gorin.jp" >Japan - Gorin</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

316. Line 3233, Column 47: document type does not allow element "option" here

     <option value="http://www.nhk.or.jp/olympic " >Japan - NHK</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

317. Line 3234, Column 44: document type does not allow element "option" here

     <option value="http://www.nhk-ondemand.jp" >Japan - NHK On Demand</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

318. Line 3235, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Jordan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

319. Line 3236, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Jordan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

320. Line 3237, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Kazakhstan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

321. Line 3238, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Kazakhstan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

322. Line 3239, Column 42: document type does not allow element "option" here

     <option value="http://olympic.sbs.co.kr" >Korea - SBS</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

323. Line 3240, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Kyrgyzstan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

324. Line 3241, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Kyrgyzstan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

325. Line 3242, Column 36: document type does not allow element "option" here

     <option value="http://www.ltv7.lv" >Latvia - LTV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

326. Line 3243, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Latvia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

327. Line 3244, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Latvia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

328. Line 3245, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Lebanon - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

329. Line 3246, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Lebanon - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

330. Line 3247, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Libya - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

331. Line 3248, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Libya - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

332. Line 3249, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Liechtenstein - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

333. Line 3250, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Liechtenstein - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

334. Line 3251, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Lithuania - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

335. Line 3252, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Lithuania - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

336. Line 3253, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Luxembourg - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

337. Line 3254, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Luxembourg - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

338. Line 3255, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Madeira - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

339. Line 3256, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Madeira - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

340. Line 3257, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Malta - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

341. Line 3258, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Malta - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

342. Line 3259, Column 54: document type does not allow element "option" here

     …tp://jo-vancouver-2010.francetv.fr" >Martinique - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

343. Line 3260, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Martinique - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

344. Line 3261, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Martinique - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

345. Line 3262, Column 54: document type does not allow element "option" here

     <option value="http://jo-vancouver-2010.francetv.fr" >Mayotte - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

346. Line 3263, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Mayotte - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

347. Line 3264, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Mayotte - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

348. Line 3265, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >Mexico - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

349. Line 3266, Column 44: document type does not allow element "option" here

     … value="http://eurosport.yahoo.com" >Moldova, Republic Of - Eurosport</opti…

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

350. Line 3267, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >Moldova, Republic Of - Eurovision</opti…

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

351. Line 3268, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Monaco - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

352. Line 3269, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Monaco - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

353. Line 3270, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Montenegro - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

354. Line 3271, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Montenegro - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

355. Line 3272, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Morocco - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

356. Line 3273, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Morroco - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

357. Line 3274, Column 38: document type does not allow element "option" here

     <option value="http://nos.nl/os2010" >Netherlands - NOS</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

358. Line 3275, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Netherlands - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

359. Line 3276, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Netherlands - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

360. Line 3277, Column 42: document type does not allow element "option" here

     <option value="http://www.nos.nl/os2010" >Netherlands Antilles</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

361. Line 3278, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Netherlands Antilles</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

362. Line 3279, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >Netherlands Antilles - Eurovision</opti…

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

363. Line 3280, Column 54: document type does not allow element "option" here

     …tp://jo-vancouver-2010.francetv.fr" >New Caledonia - France Télévisions</opti

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

364. Line 3281, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >New Caledonia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

365. Line 3282, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >New Caledonia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

366. Line 3283, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >Nicaragua - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

367. Line 3284, Column 38: document type does not allow element "option" here

     <option value="http://www.nrk.no/ol" >Norway - NRK</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

368. Line 3285, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Norway - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

369. Line 3286, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Norway - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

370. Line 3287, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >Panama - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

371. Line 3288, Column 65: document type does not allow element "option" here

     …="http://www.pe.terra.com/deportes/vancouver2010/" >Peru - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

372. Line 3289, Column 45: document type does not allow element "option" here

     <option value="http://vancouver2010.tvp.pl" >Poland - TVP</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

373. Line 3290, Column 37: document type does not allow element "option" here

     <option value="http://eurosport.pl" >Poland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

374. Line 3291, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Poland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

375. Line 3292, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Portugal - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

376. Line 3293, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Portugal - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

377. Line 3294, Column 54: document type does not allow element "option" here

     <option value="http://jo-vancouver-2010.francetv.fr" >Réunion - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

378. Line 3295, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Réunion - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

379. Line 3296, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Réunion - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

380. Line 3297, Column 43: document type does not allow element "option" here

     <option value="http://www.tvr.ro/Joiarna" >Romania - TVR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

381. Line 3298, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Romania - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

382. Line 3299, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Romania - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

383. Line 3300, Column 38: document type does not allow element "option" here

     <option value="http://eurosport.ru " >Russia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

384. Line 3301, Column 41: document type does not allow element "option" here

     <option value="http://www.1tv.ru/olimp" >Russia - C1R</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

385. Line 3302, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Russia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

386. Line 3303, Column 57: document type does not allow element "option" here

     <option value="http://video.sportbox.ru/olimpiada 2010" >Russia - RTR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

387. Line 3304, Column 54: document type does not allow element "option" here

     …tp://jo-vancouver-2010.francetv.fr" >Saint Pierre And Miquelon - France Télév

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

388. Line 3305, Column 44: document type does not allow element "option" here

     … value="http://eurosport.yahoo.com" >Saint Pierre And Miquelon - Eurosport</o

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

389. Line 3306, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >Saint Pierre And Miquelon - Eurovision</

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

390. Line 3307, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >San Marino - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

391. Line 3308, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >San Marino - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

392. Line 3309, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Serbia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

393. Line 3310, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Serbia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

394. Line 3311, Column 45: document type does not allow element "option" here

     <option value="http://www.stv.sk/vancouver" >Slovakia - STV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

395. Line 3312, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Slovakia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

396. Line 3313, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Slovakia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

397. Line 3314, Column 45: document type does not allow element "option" here

     <option value="http://www.rtvslo.si/oi2010" >Slovenia - RTV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

398. Line 3315, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Slovenia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

399. Line 3316, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Slovenia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

400. Line 3317, Column 51: document type does not allow element "option" here

     <option value="http://www.rtve.es/vancouver-2010" >Spain - RTVE</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

401. Line 3318, Column 48: document type does not allow element "option" here

     <option value="http://es.eurosport.yahoo.com " >Spain - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

402. Line 3319, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Spain - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

403. Line 3320, Column 41: document type does not allow element "option" here

     <option value="http://www.nrksport.net" >Spitsbergen - NRK</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

404. Line 3321, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Spitsbergen - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

405. Line 3322, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Spitsbergen - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

406. Line 3323, Column 38: document type does not allow element "option" here

     <option value="http://www.svt.se/os" >Sweden - SVT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

407. Line 3324, Column 38: document type does not allow element "option" here

     <option value="http://eurosport.se " >Sweden - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

408. Line 3325, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Sweden - Eurovision </option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

409. Line 3326, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Switzerland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

410. Line 3327, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Switzerland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

411. Line 3328, Column 45: document type does not allow element "option" here

     <option value="http://www.rsi.ch/vancouver" >Switzerland - RSI</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

412. Line 3329, Column 44: document type does not allow element "option" here

     <option value="http://vancouver2010.sf.tv" >Switzerland - SF</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

413. Line 3330, Column 54: document type does not allow element "option" here

     <option value="http://www.tsrsport.ch/vancouver2010" >Switzerland - TSR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

414. Line 3331, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Tajikistan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

415. Line 3332, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Tajikistan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

416. Line 3333, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >The Azores - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

417. Line 3334, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >The Azores - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

418. Line 3335, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Tunisia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

419. Line 3336, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Tunisia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

420. Line 3337, Column 39: document type does not allow element "option" here

     <option value="http://www.trt.net.tr" >Turkey - TRT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

421. Line 3338, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Turkey - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

422. Line 3339, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Turkey - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

423. Line 3340, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Turkmenistan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

424. Line 3341, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Turkmenistan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

425. Line 3342, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Ukraine - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

426. Line 3343, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Ukraine - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

427. Line 3344, Column 44: document type does not allow element "option" here

     <option value="http://www.bbc.co.uk/sport" >United Kingdom - BBC</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

428. Line 3345, Column 47: document type does not allow element "option" here

     <option value="http://uk.eurosport.yahoo.com" >United Kingdom - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

429. Line 3346, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >United Kingdom - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

430. Line 3347, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >Uruguay - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

431. Line 3348, Column 44: document type does not allow element "option" here

     <option value="http://www.nbcolympics.com" >USA - NBC</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

432. Line 3349, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Uzbekistan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

433. Line 3350, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Uzbekistan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

434. Line 3351, Column 44: document type does not allow element "option" here

     … value="http://eurosport.yahoo.com" >Vatican City State (Holy See) - Eurospor

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

435. Line 3352, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >Vatican City State (Holy See) - Eurovisi

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

436. Line 3353, Column 65: document type does not allow element "option" here

     …="http://www.ve.terra.com/deportes/vancouver2010/" >Venezuela - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

437. Line 3354, Column 44: document type does not allow element "option" here

     <option value="http://www.bbc.co.uk/sport" >Virgin Islands, British</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

438. Line 3355, Column 44: document type does not allow element "option" here

     … value="http://eurosport.yahoo.com" >Virgin Islands, British - Eurosport</opt

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

439. Line 3356, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >Virgin Islands, British - Eurovision</op

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

440. Line 3357, Column 54: document type does not allow element "option" here

     …tp://jo-vancouver-2010.francetv.fr" >Wallis And Futuna - France Télévisions</

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

441. Line 3358, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Wallis And Futuna - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

442. Line 3359, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Wallis And Futuna - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

443. Line 3360, Column 9: end tag for "body" omitted, but OMITTAG NO was specified

     </select>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

444. Line 3110: start tag was here

     ><body>

445. Line 3360, Column 9: end tag for "html" omitted, but OMITTAG NO was specified

     </select>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

446. Line 3105: start tag was here

     ><html xmlns="http://www.w3.org/1999/xhtml">

447. Line 3461, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …nternational Olympic Committee" rel=nofollow><img src="/gfx/00/17/22/ioc_18d-

     ✉

448. Line 3462, Column 107: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …apore Youth Olympic Games 2010" rel=nofollow><img src="/gfx/00/13/35/singapor

     ✉

449. Line 3463, Column 81: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …et="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-2

     ✉

450. Line 3464, Column 77: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …get="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-20

     ✉

451. Line 3465, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …arget="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18/99/rio2016_

     ✉

452. Line 3535, Column 5: document type does not allow element "ul" here; assuming missing "li" start-tag

      <ul><br />

     ✉

453. Line 3535, Column 11: document type does not allow element "br" here; assuming missing "li" start-tag

      <ul><br />

     ✉

454. Line 3537, Column 5: document type does not allow element "li" here; missing one of "ul", "ol" start-tag

      <li><a href="/more-2010-information/olympic-torch-relay/olympic-torch-relay-int

     ✉

     The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

     One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

455. Line 3542, Column 5: document type does not allow element "li" here; missing one of "ul", "ol" start-tag

      <li><a href="/more-2010-information/olympic-torch-relay/about-the-olympic-torch

     ✉

     The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

     One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

456. Line 3543, Column 7: end tag for "li" omitted, but OMITTAG NO was specified

      </div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

457. Line 3535, Column 5: start tag was here

      <ul><br />

458. Line 3543, Column 7: end tag for "ul" omitted, but OMITTAG NO was specified

      </div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

459. Line 3535, Column 1: start tag was here

      <ul><br />

460. Line 3543, Column 7: end tag for "li" omitted, but OMITTAG NO was specified

      </div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

461. Line 3535, Column 1: start tag was here

      <ul><br />

462. Line 3543, Column 7: end tag for "ul" omitted, but OMITTAG NO was specified

      </div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

463. Line 3531, Column 1: start tag was here

      <ul>

464. Line 3574, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     			<li><a href="/olympic-news/rss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

465. Line 3613, Column 36: character "&amp;" is the first character of a delimiter but occurred as data

      if (!(typeof nad === "undefined") && !nad)

     ✉

     This message may appear in several cases:

     • You tried to include the "<" character in your page: you should escape it as "&lt;"
     • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
     • Another possibility is that you forgot to close quotes in a previous tag.
466. Line 3613, Column 37: character "&amp;" is the first character of a delimiter but occurred as data

      if (!(typeof nad === "undefined") && !nad)

     ✉

     This message may appear in several cases:

     • You tried to include the "<" character in your page: you should escape it as "&lt;"
     • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
     • Another possibility is that you forgot to close quotes in a previous tag.
467. Line 169, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

     …d = document.location.protocol == "https:";    if (!nad) document.write(unesc…

     ✉

468. Line 169, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

     …d = document.location.protocol == "https:";    if (!nad) document.write(unesc…

     ✉

469. Line 244, Column 30: XML Parsing Error: AttValue: " or ' expected

     document.writeln('<style type=\"text/css\">');

     ✉

470. Line 244, Column 30: XML Parsing Error: attributes construct error

     document.writeln('<style type=\"text/css\">');

     ✉

471. Line 244, Column 30: XML Parsing Error: Couldn't find end of Start Tag style line 244

     document.writeln('<style type=\"text/css\">');

     ✉

472. Line 247, Column 26: XML Parsing Error: Opening and ending tag mismatch: script line 199 and style

     document.writeln('</style>');

     ✉

473. Line 248, Column 9: XML Parsing Error: Opening and ending tag mismatch: meta line 24 and script

     </script>

     ✉

474. Line 1121, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

     …/schedule---results/" title="Schedule & Results">Schedule & Results</a></li>…

     ✉

475. Line 1121, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

     …/schedule---results/" title="Schedule & Results">Schedule & Results</a></li>…

     ✉

476. Line 1232, Column 27: XML Parsing Error: AttValue: " or ' expected

     document.write("<div style=\"position:relative; height: 293px;\"><div style=\"po

     ✉

477. Line 1232, Column 27: XML Parsing Error: attributes construct error

     document.write("<div style=\"position:relative; height: 293px;\"><div style=\"po

     ✉

478. Line 1232, Column 27: XML Parsing Error: Couldn't find end of Start Tag div line 1232

     document.write("<div style=\"position:relative; height: 293px;\"><div style=\"po

     ✉

479. Line 1232, Column 76: XML Parsing Error: AttValue: " or ' expected

     …on:relative; height: 293px;\"><div style=\"position:absolute; left: -19px;\">");

     ✉

480. Line 1232, Column 76: XML Parsing Error: attributes construct error

     …on:relative; height: 293px;\"><div style=\"position:absolute; left: -19px;\">");

     ✉

481. Line 1232, Column 76: XML Parsing Error: Couldn't find end of Start Tag div line 1232

     …on:relative; height: 293px;\"><div style=\"position:absolute; left: -19px;\">");

     ✉

482. Line 1248, Column 22: XML Parsing Error: Opening and ending tag mismatch: script line 1225 and div

     document.write("</div></div>");

     ✉

483. Line 1254, Column 9: XML Parsing Error: Opening and ending tag mismatch: div line 1168 and script

     </script>

     ✉

484. Line 1873, Column 76: XML Parsing Error: EntityRef: expecting ';'

     …tore/?utm_campaign=believe&utm_medium=banner&utm_source=main&utm_content=en" 

     ✉

485. Line 1873, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …/?utm_campaign=believe&utm_medium=banner&utm_source=main&utm_content=en" titl…

     ✉

486. Line 1873, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …/?utm_campaign=believe&utm_medium=banner&utm_source=main&utm_content=en" titl…

     ✉

487. Line 1898, Column 37: XML Parsing Error: xmlParseEntityRef: no name

       if (!(typeof nad === "undefined") && !nad)

     ✉

488. Line 1898, Column 38: XML Parsing Error: xmlParseEntityRef: no name

       if (!(typeof nad === "undefined") && !nad)

     ✉

489. Line 2340, Column 37: XML Parsing Error: xmlParseEntityRef: no name

       if (!(typeof nad === "undefined") && !nad)

     ✉

490. Line 2340, Column 38: XML Parsing Error: xmlParseEntityRef: no name

       if (!(typeof nad === "undefined") && !nad)

     ✉

491. Line 2891, Column 37: XML Parsing Error: xmlParseEntityRef: no name

       if (!(typeof nad === "undefined") && !nad)

     ✉

492. Line 2891, Column 38: XML Parsing Error: xmlParseEntityRef: no name

       if (!(typeof nad === "undefined") && !nad)

     ✉

493. Line 2928, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …de/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Aler

     ✉

494. Line 2928, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …rts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</op…

     ✉

495. Line 2928, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …rts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</op…

     ✉

496. Line 2929, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …de/alerts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Aler

     ✉

497. Line 2929, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …rts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</op…

     ✉

498. Line 2929, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …rts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</op…

     ✉

499. Line 2930, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …de/alerts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</o

     ✉

500. Line 2930, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …rts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>…

     ✉

501. Line 2930, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …rts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>…

     ✉

502. Line 3104, Column 1: XML Parsing Error: StartTag: invalid element name

     <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.or

     ✉

503. Line 3360, Column 9: XML Parsing Error: Opening and ending tag mismatch: body line 3110 and select

     </select>

     ✉

504. Line 3361, Column 7: XML Parsing Error: Opening and ending tag mismatch: html line 3105 and form

     </form>

     ✉

505. Line 3362, Column 6: XML Parsing Error: Opening and ending tag mismatch: select line 3102 and div

     </div>

     ✉

506. Line 3363, Column > 80: XML Parsing Error: Opening and ending tag mismatch: form line 3101 and div

     …line" src="/gfx/00/23/57/broadcaster2_00d-ku.jpg" /></div>…

     ✉

507. Line 3461, Column > 80: XML Parsing Error: AttValue: " or ' expected

     …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

508. Line 3461, Column > 80: XML Parsing Error: attributes construct error

     …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

509. Line 3461, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 3461

     …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

510. Line 3461, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 3461 and a

     …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

511. Line 3461, Column > 80: XML Parsing Error: Opening and ending tag mismatch: ul line 3460 and li

     …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

512. Line 3462, Column > 80: XML Parsing Error: AttValue: " or ' expected

     …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

513. Line 3462, Column > 80: XML Parsing Error: attributes construct error

     …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

514. Line 3462, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 3462

     …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

515. Line 3462, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 3462 and a

     …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

516. Line 3462, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 3458 and li

     …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

517. Line 3463, Column > 80: XML Parsing Error: AttValue: " or ' expected

     …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

518. Line 3463, Column > 80: XML Parsing Error: attributes construct error

     …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

519. Line 3463, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 3463

     …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

520. Line 3463, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 3463 and a

     …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

521. Line 3463, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 3457 and li

     …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

522. Line 3464, Column 76: XML Parsing Error: AttValue: " or ' expected

     …rget="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2

     ✉

523. Line 3464, Column 76: XML Parsing Error: attributes construct error

     …rget="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2

     ✉

524. Line 3464, Column 76: XML Parsing Error: Couldn't find end of Start Tag a line 3464

     …rget="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2

     ✉

525. Line 3464, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 3464 and a

     …="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2014_…

     ✉

526. Line 3464, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 3440 and li

     …="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2014_…

     ✉

527. Line 3465, Column > 80: XML Parsing Error: AttValue: " or ' expected

     …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

528. Line 3465, Column > 80: XML Parsing Error: attributes construct error

     …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

529. Line 3465, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 3465

     …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

530. Line 3465, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 3465 and a

     …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

531. Line 3465, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 275 and li

     …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

532. Line 3466, Column 6: XML Parsing Error: Opening and ending tag mismatch: div line 274 and ul

      </ul>

     ✉

533. Line 3543, Column 7: XML Parsing Error: Opening and ending tag mismatch: ul line 3535 and div

      </div>

     ✉

534. Line 3562, Column 8: XML Parsing Error: Opening and ending tag mismatch: ul line 3531 and div

     		</div><!-- end of refLine -->

     ✉

535. Line 3574, Column 58: XML Parsing Error: AttValue: " or ' expected

     			<li><a href="/olympic-news/rss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

536. Line 3574, Column 58: XML Parsing Error: attributes construct error

     			<li><a href="/olympic-news/rss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

537. Line 3574, Column 58: XML Parsing Error: Couldn't find end of Start Tag a line 3574

     			<li><a href="/olympic-news/rss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

538. Line 3574, Column 74: XML Parsing Error: Opening and ending tag mismatch: li line 3574 and a

     …ss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

539. Line 3574, Column > 80: XML Parsing Error: Opening and ending tag mismatch: ul line 3566 and li

     … title="RSS" rel=nofollow>RSS</a></li>…

     ✉

540. Line 3575, Column 5: XML Parsing Error: Opening and ending tag mismatch: div line 3565 and ul

     </ul>

     ✉

541. Line 3582, Column 7: XML Parsing Error: Opening and ending tag mismatch: body line 263 and div

      </div>

     ✉

542. Line 3601, Column 7: XML Parsing Error: Opening and ending tag mismatch: html line 2 and div

     	</div><!--end of wrapFooter-->

     ✉

543. Line 3612, Column 2: XML Parsing Error: Extra content at the end of the document

     		<script type="text/javascript">

     ✉

↑ Top